This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Global: add global validators to settings #2078
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
ValidateInstanceInContext
split into maya and nuke pluginValidateIntent
is for all hosts by default and added profiles to filter validations (by default is plugin disabled)ValidateVersion
addedactive
attribute to be able define if is activated by defaultQUESTIONS
ValidateContainers
- currently has settings in each host settings and not sure if should be added to global publish plugins settings and if yes than it will probably need profiles but at the same time should haveoptional
(maybe) does it make sense to have bothoptional
+active
andprofiles
under that?is required does not need settingsValidateResources
I actually don't know why are resources validated?